-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TST: Reproduce paintEvent failures #7294
Conversation
Codecov Report
@@ Coverage Diff @@
## master #7294 +/- ##
==========================================
+ Coverage 87.60% 90.07% +2.46%
==========================================
Files 454 454
Lines 82558 82391 -167
Branches 13050 13023 -27
==========================================
+ Hits 72329 74216 +1887
+ Misses 7426 5352 -2074
- Partials 2803 2823 +20 |
Closing now since this seems to be solved by #7295 |
The failures still occur. Reference: |
I was able to read it when you did the comment but I forgot to save the log, now the build is not available anymore. I remember it was related somehow to |
Just go through the recent Azure builds, it usually only takes looking at a few to find a failure with a good traceback, like: |
For reference, here is a log:
|
Travis even hit one: https://travis-ci.org/mne-tools/mne-python/jobs/655188026#L2938-L2944 |
Reproduced in here, it appears to be consistent. |
My first idea is to use the |
Test 1) is green |
This reverts commit 7f6120b.
e26d41d
to
fe70356
Compare
Travis jobs are up in here, waiting for the good news 🤞 |
thx @GuillaumeFavelier ! |
1 similar comment
thx @GuillaumeFavelier ! |
times, array, self.interp_kind, axis=1, | ||
assume_sorted=True)(time_idx) | ||
ifunc = interp1d(times, self._data['time']) | ||
act_time = ifunc(time_idx) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR undid (again) some of the refactoring. The way my commits worked:
- the interpolators were set up once and reused (efficiency)
- a helper _safe_interp1d (avoids bugs now back in master)
And this commit appears to have un-done these. Accordingly we have lost the efficiency and the singleton regression is back in master
:
I think the real (only) bug that probably needed to be fixed here had to do with calling the interpolation functions incorrectly, right? If so @GuillaumeFavelier can you make a revert commit for this PR and try making the minimal changes required to get CIs happy again? I'd rather not sacrifice the _safe_interp1d
and funcs
efficiency gains...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahh it's even more extensive -- I see this started out by completely reverting #7257. Are we planning on putting that back in somehow?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated #7162 and delayed thoses features to 0.21 for now
The goal is to fix the Azure failures encountered recently during testing in: #7290, #7235
The log is very scarce, I'm trying locally with
virtualbox
at the same time: